K2 Concepts - Synchronous and Asynchronous Events

When configuring the IPC Event Wizard, the developer must select between a synchronous or asynchronous events. When presented with this option, the consideration is what should the parent process do, once the child process has been planned? The answer depends on whether the parent process is dependant on the child process for a response before it can continue running.

In circumstances where the parent requires a response from the child process, this a synchronous process or a series process. When the parent process requires no response from the child process, this is an asynchronous process. The parent and the child processes run in parallel from the point when the parent process planned the child.

Considerations

Consideration must be given to when an IPC is employed to accomplish a separate task. IPCs can prevent a parent process from completing when waiting for a response from a child process. Incorrect configuration of the IPC can have the same result, for example, the process is set to Synchronous however no value is returned. The parent process therefore waits indefinitely for a response that never takes place.

IPC and the Default Activity

When used, the rule of thumb is to maintain the minimum number of Events in the same Default activity as the IPC. This will reduce the possibility of critical events, if any from being delayed owing to an IPC. Where possible an IPC sequestered in an independent Default Activity is good practice.